@btardif : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Learn Build status updates of commit e8e8443:

✅ Validation status: passed

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

PRMerger Results

@genlin

For LWASv1 / docker pull to support this, the registry needs to be added as an "insecure registry" on docker startup (dockerd | Docker Docs), which is something we only do for Internal Registry Roles where enabled.

For LWASv2 image pull to support this, a specific flag needs to be present (something akin to --plain-http=true), and this is again something that is only present when we pull platform images from the Internal Registry Roles.

I don't believe HTTP pull for private registries has ever been a supported scenario.

@btardif hold up this might not even be correct to begin with, let me follow up with you offline.

@btardif I noticed this PR is currently on hold. Once it's ready for merge, type "#sign-off" in a new comment.